-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat(nextjs): Improve logs documentation with split-view layout #15919
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Create dedicated Next.js logs page with full SplitLayout - Add Best Practices section (wide events, business context, naming) - Use table format for default attributes (easier to scan) - Add enableLogs to Edge config in quickstart - Create Next.js-specific setup include with all 3 runtime configs 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
9dde7d9 to
3175e42
Compare
…ctions - Add sidebar_section: features to show under FEATURES nav - Add new: true for sidebar NEW badge - Remove StepComponent wrapper (sections aren't sequential steps) - Use markdown ## for Default Attributes (shows in TOC) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
- Add sidebar_title: Logs to fix FEATURES section placement - Inline all integrations content with SplitLayout - Console, Pino, Consola, Winston each get split view treatment 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
…ple payload - Remove FeatureBadge (sidebar badge is enough) - Inline integrations with split-view layout - Add Upcoming Integrations section - Replace attribute tables with annotated JSON sample - Add Troubleshooting section (enableLogs, dropped logs, filtered data) - Add payload_size attribute 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Dedicated page has inline content, platform-include not needed. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Platform-include needed for common logs page fallback. Next.js is unique because it requires enableLogs in 3 config files. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
chargome
approved these changes
Jan 8, 2026
Member
chargome
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
philipphofmann
pushed a commit
that referenced
this pull request
Jan 9, 2026
## Summary Redesigns the Next.js Logs documentation with improved layout and content: - **Split-view layout** — Text explanations on left, code examples on right - **Inlined integrations** — Console, Pino, Consola, Winston with split-view - **Sample payload** — Shows all default attributes in context (replaces verbose tables) - **Troubleshooting section** — Common issues: enableLogs config, dropped logs, filtered data - **Best practices** — Wide events, business context, consistent naming ## Why Next.js-specific? Next.js requires `enableLogs: true` in **3 separate config files** (client, server, edge), unlike most SDKs that have a single init. ## Future work This split-view layout can be applied to other SDK logs docs. The pattern established here (setup, usage, integrations, best practices, troubleshooting) can become the standard template. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.5 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Redesigns the Next.js Logs documentation with improved layout and content:
Why Next.js-specific?
Next.js requires
enableLogs: truein 3 separate config files (client, server, edge), unlike most SDKs that have a single init.Future work
This split-view layout can be applied to other SDK logs docs. The pattern established here (setup, usage, integrations, best practices, troubleshooting) can become the standard template.
🤖 Generated with Claude Code